Skip to content

fix(toolbox-langchain): Expose auth requirements from underlying core tool #292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

anubhav756
Copy link
Contributor

@anubhav756 anubhav756 commented Jun 19, 2025

This PR exposes the authentication and authorization requirements from the underlying toolbox-core's ToolboxTool as properties on the toolbox-langchain's ToolboxTool wrapper.

This change forwards the properties introduced in #294, making them accessible at the LangChain integration layer. It is a key prerequisite for implementing self-authenticating tools (#291), as it allows higher-level abstractions to inspect a tool's auth needs directly.

@anubhav756 anubhav756 self-assigned this Jun 19, 2025
@anubhav756 anubhav756 force-pushed the anubhav-state-lc branch 2 times, most recently from 1cef9c2 to 11f4718 Compare June 19, 2025 14:31
@anubhav756 anubhav756 changed the title fix(toolbox-langchain): Expose internal state for better debuggability fix(toolbox-langchain): Expose auth requirements from core tool Jun 19, 2025
@anubhav756 anubhav756 changed the title fix(toolbox-langchain): Expose auth requirements from core tool fix(toolbox-langchain): Expose auth requirements from underlying core tool Jun 19, 2025
@anubhav756 anubhav756 marked this pull request as ready for review June 19, 2025 15:26
@anubhav756 anubhav756 requested a review from a team as a code owner June 19, 2025 15:26
@twishabansal
Copy link
Contributor

Do we plan to add tests for this?

Base automatically changed from anubhav-state to main June 24, 2025 11:50
@anubhav756
Copy link
Contributor Author

Do we plan to add tests for this?

Added. Thanks for pointing that out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants